OCPP 2.0.1

Part 2 - Specification

Edition 2 FINAL, 2022-12-15

Table of Contents

Disclaimer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê1

Generic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê2

Version History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê3

1. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê4

1.1. OCPP 2.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê4

1.2. OCPP 2.0.1 Edition 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê4

2. Conventions, Terminology and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê5

2.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê5

2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê6

2.3. Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê8

2.4. Actors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê10

2.5. References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê11

2.6. Definition of Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê12

2.7. ISO 15118 support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê14

3. Generic Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê15

3.1. Time Format Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê15

3.2. Message Timeouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê16

3.3. Language support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê16

A. Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê17

1. OCPP Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê18

1.1. Security Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê18

1.2. Design Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê18

1.3. Security Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê19

1.4. Keys used in OCPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê26

1.5. Certificate Revocation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê28

1.6. Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê29

2. Use cases & Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê30

A01 - Update Charging Station Password for HTTP Basic Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê30

A02 - Update Charging Station Certificate by request of CSMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê31

A03 - Update Charging Station Certificate initiated by the Charging Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê35

A04 - Security Event Notification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê39

A05 - Upgrade Charging Station Security Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê40

B. Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê42

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê43

1.1. Transactions before being accepted by a CSMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê43

2. Use cases & Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê44

2.1. Booting a Charging Station. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê44

B01 - Cold Boot Charging Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê44

B02 - Cold Boot Charging Station - Pending. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê47

B03 - Cold Boot Charging Station - Rejected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê50

B04 - Offline Behavior Idle Charging Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê52

2.2. Configuring a Charging Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê53

B05 - Set Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê53

B06 - Get Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê55

B07 - Get Base Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê57

B08 - Get Custom Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê60

B09 - Setting a new NetworkConnectionProfile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê62

B10 - Migrate to new CSMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê63

2.3. Resetting a Charging Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê64

B11 - Reset - Without Ongoing Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê64

B12 - Reset - With Ongoing Transaction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê67

C. Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê70

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê71

1.1. ID Tokens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê71

1.2. Group ID Tokens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê71

1.3. Authorization Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê72

1.4. Local Authorization List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê72

1.5. Unknown Offline Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê72

2. Use cases & Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê73

2.1. Authorization options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê73

C01 - EV Driver Authorization using RFID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê73

C02 - Authorization using a start button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê77

C03 - Authorization using credit/debit card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê79

C04 - Authorization using PIN-code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê82

C05 - Authorization for CSMS initiated transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê84

C06 - Authorization using local id type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê86

2.2. ISO 15118 Authorization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê89

C07 - Authorization using Contract Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê89

C08 - Authorization at EVSE using ISO 15118 External Identification Means (EIM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê92

2.3. GroupId . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê94

C09 - Authorization by GroupId . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê94

2.4. Authorization Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê96

C10 - Store Authorization Data in the Authorization Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê96

C11 - Clear Authorization Data in Authorization Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê98

C12 - Start Transaction - Cached Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê99

2.5. Local Authorization list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê101

C13 - Offline Authorization through Local Authorization List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê101

C14 - Online Authorization through Local Authorization List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê102

2.6. Offline Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê104

C15 - Offline Authorization of unknown Id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê104

2.7. Master Pass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê106

C16 - Stop Transaction with a Master Pass. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê106

D. LocalAuthorizationList Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê109

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê110

2. Use cases & Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê111

D01 - Send Local Authorization List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê111

D02 - Get Local List Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê114

E. Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê115

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê116

1.1. Flexible transaction start/stop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê116

1.2. TransactionId generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê117

1.3. Delivering transaction-related messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê117

1.4. Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê118

1.5. Clarification for optional fields in TransactionEventRequest. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê118

2. Use cases & Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê120

2.1. OCPP transaction mechanism. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê120

E01 - Start Transaction options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê120

E02 - Start Transaction - Cable Plugin First . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê126

E03 - Start Transaction - IdToken First . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê131

E04 - Transaction started while Charging Station is offline. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê135

E05 - Start Transaction - Id not Accepted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê139

E06 - Stop Transaction options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê142

E07 - Transaction locally stopped by IdToken. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê147

E08 - Transaction stopped while Charging Station is offline. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê151

E09 - When cable disconnected on EV-side: Stop Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê154

E10 - When cable disconnected on EV-side: Suspend Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê157

E11 - Connection Loss During Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê160

E12 - Inform CSMS of an Offline Occurred Transaction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê162

E13 - Transaction-related message not accepted by CSMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê164

E14 - Check transaction status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê166

2.2. Interrupting and Stopping ISO 15118 Charging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê167

E15 - End of charging process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê167

F. RemoteControl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê169

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê170

2. Use cases & Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê171

2.1. Remote Transaction Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê171

F01 - Remote Start Transaction - Cable Plugin First. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê171

F02 - Remote Start Transaction - Remote Start First . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê175

F03 - Remote Stop Transaction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê180

F04 - Remote Stop ISO 15118 Charging from CSMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê182

2.2. Unlock Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê184

F05 - Remotely Unlock Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê184

2.3. Remote Trigger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê186

F06 - Trigger Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê186

G. Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê189

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê190

2. Use cases & Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê191

G01 - Status Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê191

G02 - Heartbeat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê193

G03 - Change Availability EVSE/Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê195

G04 - Change Availability Charging Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê197

G05 - Lock Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê199

H. Reservation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê201

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê202

2. Use cases & Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê203

H01 - Reservation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê203

H02 - Cancel Reservation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê207

H03 - Use a reserved EVSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê208

H04 - Reservation Ended, not used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê211

I. TariffAndCost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê212

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê213

1.1. Why no structured tariff information? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê213

2. Use cases & Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê214

I01 - Show EV Driver-specific Tariff Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê214

I02 - Show EV Driver Running Total Cost During Charging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê215

I03 - Show EV Driver Final Total Cost After Charging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê216

I04 - Show Fallback Tariff Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê217

I05 - Show Fallback Total Cost Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê219

I06 - Update Tariff Information During Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê220

J. MeterValues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê222

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê223

2. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê224

2.1. Transaction Meter Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê224

2.2. Clock-Aligned Meter Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê224

2.3. Multiple Locations/Phases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê225

2.4. Signed Meter Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê225

3. Use cases & Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê226

3.1. MeterValues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê226

J01 - Sending Meter Values not related to a transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê226

J02 - Sending transaction related Meter Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê229

3.2. ISO 15118 MeterValue signing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê231

J03 - Charging Loop with metering information exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê231

K. SmartCharging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê233

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê234

2. Types of Smart Charging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê235

2.1. Internal Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê235

2.2. Central Smart Charging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê235

2.3. Local Smart Charging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê236

2.4. External Smart Charging Control Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê236

3. Charging profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê238

3.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê238

3.2. Charging profile purposes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê238

3.3. Charging profile recurrency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê238

3.4. Stacking charging profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê239

3.5. Combining Charging Profile Purposes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê239

3.6. Example Charging Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê240

4. Smart Charging Signals to a Charging Station from Multiple Actors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê242

5. Use cases & Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê243

5.1. General Smart Charging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê243

K01 - SetChargingProfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê243

K02 - Central Smart Charging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê248

K03 - Local Smart Charging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê252

K04 - Internal Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê255

K05 - Remote Start Transaction with Charging Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê256

K06 - Offline Behavior Smart Charging During Transaction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê258

K07 - Offline Behavior Smart Charging at Start of Transaction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê259

K08 - Get Composite Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê261

K09 - Get Charging Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê263

K10 - Clear Charging Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê264

5.2. External Charging Limit based Smart Charging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê267

K11 - Set / Update External Charging Limit With Ongoing Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê267

K12 - Set / Update External Charging Limit Without Ongoing Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê269

K13 - Reset / Release External Charging Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê270

K14 - External Charging Limit with Local Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê272

5.3. ISO 15118 based Smart Charging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê274

K15 - Charging with load leveling based on High Level Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê274

K16 - Renegotiation initiated by CSMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê277

K17 - Renegotiation initiated by EV. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê279

L. FirmwareManagement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê283

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê284

2. Use cases & Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê285

L01 - Secure Firmware Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê285

L02 - Non-Secure Firmware Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê290

L03 - Publish Firmware file on Local Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê293

L04 - Unpublish Firmware file on Local Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê295

M. ISO 15118 CertificateManagement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê297

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê298

2. ISO 15118 Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê301

2.1. ISO 15118 Certificate structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê301

2.2. Using ISO 15118 Certificates in OCPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê302

2.3. 15118 communication set-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê303

2.4. Certificate - Use Case mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê303

3. Use cases from ISO 15118 relevant for OCPP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê305

4. Use cases & Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê306

M01 - Certificate installation EV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê306

M02 - Certificate Update EV. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê307

M03 - Retrieve list of available certificates from a Charging Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê308

M04 - Delete a specific certificate from a Charging Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê309

M05 - Install CA certificate in a Charging Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê310

M06 - Get V2G Charging Station Certificate status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê312

N. Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê314

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê315

2. Use cases & Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê316

2.1. Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê316

N01 - Retrieve Log Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê316

2.2. Configure Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê318

N02 - Get Monitoring report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê318

N03 - Set Monitoring Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê320

N04 - Set Variable Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê321

N05 - Set Monitoring Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê324

N06 - Clear / Remove Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê325

2.3. Monitoring Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê326

N07 - Alert Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê326

N08 - Periodic Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê328

2.4. Customer Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê330

N09 - Get Customer Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê330

N10 - Clear Customer Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê331

O. DisplayMessage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê334

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê335

2. Use cases & Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê336

O01 - Set DisplayMessage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê336

O02 - Set DisplayMessage for Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê338

O03 - Get All DisplayMessages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê340

O04 - Get Specific DisplayMessages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê342

O05 - Clear a DisplayMessage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê344

O06 - Replace DisplayMessage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê345

P. DataTransfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê346

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê347

2. Use cases & Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê348

P01 - Data Transfer to the Charging Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê348

P02 - Data Transfer to the CSMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê350

Messages, Datatypes & Enumerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê352

1. Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê353

1.1. Authorize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê353

1.2. BootNotification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê353

1.3. CancelReservation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê354

1.4. CertificateSigned . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê354

1.5. ChangeAvailability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê355

1.6. ClearCache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê355

1.7. ClearChargingProfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê356

1.8. ClearDisplayMessage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê356

1.9. ClearedChargingLimit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê356

1.10. ClearVariableMonitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê357

1.11. CostUpdated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê357

1.12. CustomerInformation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê358

1.13. DataTransfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê358

1.14. DeleteCertificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê359

1.15. FirmwareStatusNotification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê359

1.16. Get15118EVCertificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê360

1.17. GetBaseReport. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê360

1.18. GetCertificateStatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê361

1.19. GetChargingProfiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê361

1.20. GetCompositeSchedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê362

1.21. GetDisplayMessages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê362

1.22. GetInstalledCertificateIds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê363

1.23. GetLocalListVersion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê363

1.24. GetLog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê363

1.25. GetMonitoringReport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê364

1.26. GetReport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê365

1.27. GetTransactionStatus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê365

1.28. GetVariables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê366

1.29. Heartbeat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê366

1.30. InstallCertificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê366

1.31. LogStatusNotification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê367

1.32. MeterValues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê367

1.33. NotifyChargingLimit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê367

1.34. NotifyCustomerInformation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê368

1.35. NotifyDisplayMessages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê368

1.36. NotifyEVChargingNeeds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê369

1.37. NotifyEVChargingSchedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê369

1.38. NotifyEvent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê370

1.39. NotifyMonitoringReport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê370

1.40. NotifyReport. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê371

1.41. PublishFirmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê371

1.42. PublishFirmwareStatusNotification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê372

1.43. ReportChargingProfiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê372

1.44. RequestStartTransaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê373

1.45. RequestStopTransaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê373

1.46. ReservationStatusUpdate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê374

1.47. ReserveNow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê374

1.48. Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê375

1.49. SecurityEventNotification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê375

1.50. SendLocalList . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê375

1.51. SetChargingProfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê376

1.52. SetDisplayMessage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê377

1.53. SetMonitoringBase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê377

1.54. SetMonitoringLevel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê378

1.55. SetNetworkProfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê379

1.56. SetVariableMonitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê379

1.57. SetVariables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê379

1.58. SignCertificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê380

1.59. StatusNotification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê380

1.60. TransactionEvent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê381

1.61. TriggerMessage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê382

1.62. UnlockConnector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê383

1.63. UnpublishFirmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê383

1.64. UpdateFirmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê384

2. Datatypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê385

2.1. ACChargingParametersType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê385

2.2. AdditionalInfoType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê385

2.3. APNType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê385

2.4. AuthorizationData . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê386

2.5. CertificateHashDataChainType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê386

2.6. CertificateHashDataType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê386

2.7. ChargingLimitType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê386

2.8. ChargingNeedsType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê387

2.9. ChargingProfileCriterionType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê387

2.10. ChargingProfileType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê387

2.11. ChargingSchedulePeriodType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê388

2.12. ChargingScheduleType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê388

2.13. ChargingStationType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê389

2.14. ClearChargingProfileType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê389

2.15. ClearMonitoringResultType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê390

2.16. ComponentType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê390

2.17. ComponentVariableType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê390

2.18. CompositeScheduleType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê390

2.19. ConsumptionCostType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê391

2.20. CostType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê391

2.21. DCChargingParametersType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê391

2.22. EventDataType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê392

2.23. EVSEType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê392

2.24. FirmwareType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê393

2.25. GetVariableDataType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê393

2.26. GetVariableResultType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê393

2.27. IdTokenInfoType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê394

2.28. IdTokenType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê394

2.29. LogParametersType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê395

2.30. MessageContentType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê395

2.31. MessageInfoType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê395

2.32. MeterValueType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê396

2.33. ModemType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê396

2.34. MonitoringDataType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê396

2.35. NetworkConnectionProfileType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê396

2.36. OCSPRequestDataType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê397

2.37. RelativeTimeIntervalType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê397

2.38. ReportDataType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê397

2.39. SalesTariffEntryType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê398

2.40. SalesTariffType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê398

2.41. SampledValueType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê398

2.42. SetMonitoringDataType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê399

2.43. SetMonitoringResultType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê400

2.44. SetVariableDataType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê401

2.45. SetVariableResultType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê402

2.46. SignedMeterValueType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê402

2.47. StatusInfoType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê402

2.48. TransactionType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê403

2.49. UnitOfMeasureType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê403

2.50. VariableAttributeType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê403

2.51. VariableCharacteristicsType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê404

2.52. VariableMonitoringType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê404

2.53. VariableType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê405

2.54. VPNType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê406

3. Enumerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê407

3.1. APNAuthenticationEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê407

3.2. AttributeEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê407

3.3. AuthorizationStatusEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê407

3.4. AuthorizeCertificateStatusEnumType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê407

3.5. BootReasonEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê408

3.6. CancelReservationStatusEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê408

3.7. CertificateActionEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê408

3.8. CertificateSignedStatusEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê409

3.9. CertificateSigningUseEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê409

3.10. ChangeAvailabilityStatusEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê409

3.11. ChargingLimitSourceEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê409

3.12. ChargingProfileKindEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê410

3.13. ChargingProfilePurposeEnumType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê410

3.14. ChargingProfileStatusEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê410

3.15. ChargingRateUnitEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê410

3.16. ChargingStateEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê411

3.17. ClearCacheStatusEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê411

3.18. ClearChargingProfileStatusEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê411

3.19. ClearMessageStatusEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê412

3.20. ClearMonitoringStatusEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê412

3.21. ComponentCriterionEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê412

3.22. ConnectorEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê412

3.23. ConnectorStatusEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê413

3.24. CostKindEnumType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê413

3.25. CustomerInformationStatusEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê414

3.26. DataEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê414

3.27. DataTransferStatusEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê414

3.28. DeleteCertificateStatusEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê414

3.29. DisplayMessageStatusEnumType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê415

3.30. EnergyTransferModeEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê415

3.31. EventNotificationEnumType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê415

3.32. EventTriggerEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê415

3.33. FirmwareStatusEnumType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê416

3.34. GenericDeviceModelStatusEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê416

3.35. GenericStatusEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê417

3.36. GetCertificateIdUseEnumType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê417

3.37. GetCertificateStatusEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê417

3.38. GetChargingProfileStatusEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê417

3.39. GetDisplayMessagesStatusEnumType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê417

3.40. GetInstalledCertificateStatusEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê418

3.41. GetVariableStatusEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê418

3.42. HashAlgorithmEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê418

3.43. IdTokenEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê418

3.44. InstallCertificateStatusEnumType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê419

3.45. InstallCertificateUseEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê419

3.46. Iso15118EVCertificateStatusEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê419

3.47. LocationEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê419

3.48. LogEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê420

3.49. LogStatusEnumType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê420

3.50. MeasurandEnumType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê420

3.51. MessageFormatEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê421

3.52. MessagePriorityEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê422

3.53. MessageStateEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê422

3.54. MessageTriggerEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê422

3.55. MonitorEnumType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê423

3.56. MonitoringBaseEnumType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê423

3.57. MonitoringCriterionEnumType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê423

3.58. MutabilityEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê423

3.59. NotifyEVChargingNeedsStatusEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê424

3.60. OCPPInterfaceEnumType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê424

3.61. OCPPTransportEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê424

3.62. OCPPVersionEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê424

3.63. OperationalStatusEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê425

3.64. PhaseEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê425

3.65. PublishFirmwareStatusEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê425

3.66. ReadingContextEnumType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê426

3.67. ReasonEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê426

3.68. RecurrencyKindEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê427

3.69. RegistrationStatusEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê427

3.70. ReportBaseEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê427

3.71. RequestStartStopStatusEnumType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê428

3.72. ReservationUpdateStatusEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê428

3.73. ReserveNowStatusEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê428

3.74. ResetEnumType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê429

3.75. ResetStatusEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê429

3.76. SendLocalListStatusEnumType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê429

3.77. SetMonitoringStatusEnumType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê429

3.78. SetNetworkProfileStatusEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê430

3.79. SetVariableStatusEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê430

3.80. TransactionEventEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê430

3.81. TriggerMessageStatusEnumType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê430

3.82. TriggerReasonEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê431

3.83. UnlockStatusEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê431

3.84. UnpublishFirmwareStatusEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê432

3.85. UpdateEnumType . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê432

3.86. UpdateFirmwareStatusEnumType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê432

3.87. UploadLogStatusEnumType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê432

3.88. VPNEnumType. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê433

Referenced Components and Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê434

1. Controller Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê435

2. Referenced Components and Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê436

2.1. General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê436

2.2. Security related . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê444

2.3. Authorization related. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê446

2.4. Authorization Cache related. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê448

2.5. Local Authorization List Management related. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê449

2.6. Transaction related . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê450

2.7. Metering related. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê453

2.8. Reservation related . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê458

2.9. Smart Charging related . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê458

2.10. Tariff & Cost related . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê461

2.11. Diagnostics related . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê462

2.12. Display Message related . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê464

2.13. Charging Infrastructure related . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê465

2.14. ISO 15118 Related. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ê468

Disclaimer

This document is made available under the *Creative Commons Attribution-NoDerivatives 4.0 International Public License*

(https://creativecommons.org/licenses/by-nd/4.0/legalcode).

Edition 2 FINAL, 2022-12-15

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 1/471 Part 2 - Specification

Generic

Edition 2 FINAL, 2022-12-15 Generic

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 2/471 Part 2 - Specification

Version History

Version Date Description

2.0.1 Edition 2

2022-12-15 OCPP 2.0.1 Edition 2. All errata from OCPP 2.0.1 Part 2 - Errata v2.0 have been

merged into this version of the specification.

2.0.1

2020-03-31 Final version of OCPP 2.0.1

2.0

2018-04-11

OCPP 2.0 April 2018

First major release since 1.0.

Lots of new/improved/revised functionality

Revised documentation

Edition 2 FINAL, 2022-12-15 Generic

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 3/471 Part 2 - Specification

1. Scope

This document defines the protocol used between a Charging Station and a Charging Station Management System in an EV

charging infrastructure in the form of use cases. If the protocol requires a certain action or response from one side or the other,

then this will be stated in this document.

This part of the specification does not define the communication technology. In order to ensure widespread compatibility OCPP

2.0.1 is limited to JSON. The specifications for the JSON implementation are in "Part 4 - JSON over WebSockets implementation

guide".

1.1. OCPP 2.0.1

This specification defines version 2.0.1 of OCPP.

After the release of OCPP 2.0, some issues were found in OCPP 2.0. Some of these issues could not be fixed issuing errata to the

specification text only, as has been done with OCPP 1.6, but required changes to the protocol’s machine-readable schema

definition files that cannot be backward compatible.

To prevent confusion in the market and possible interoperability issues in the field, OCA has decided to name this version: 2.0.1.

OCPP 2.0.1 contains fixes for all the known issues, to date, not only the fixes to the messages.

This version replaces OCPP 2.0. OCA advises implementers of OCPP to no longer implement OCPP 2.0 and only use version 2.0.1

going forward.

As a rule, existing numbered requirements are only updated or removed, previously used requirements numbers are never reused

for a totally different requirement.

Any mentions of "OCPP 2.0" refers to revision 2.0.1 unless specifically stated otherwise.

1.2. OCPP 2.0.1 Edition 2

Two errata have been released for part 2 of the OCPP 2.0.1 specification.:“OCPP-2.0.1_part2_errata_v1_0” was released in 2021. In

2022 this was extended with additional errata entries in “OCPP-2.0.1_part2_errata_v2_0”.

These errata have been incorporated in this document, “OCPP-2.0.1_part2_specification_edition2”, such that it is no longer

necessary to read the errata in addition to the specification. The incorporation of the errata in edition 2 does not affect any

schemas of OCPP messages. Certain errata did contain changes to requirements or even new requirements, but only in cases

where a requirement contains an obvious error and would not or could not be implemented literally. New requirements were only

added when they were already implicitly there. These changes have been discussed in or were proposed by the Technology

Working Group of the Open Charge Alliance.

The appendices of the OCPP 2.0.1 part 2 can be updated without requiring a new OCPP release. This mainly concerns the

components and variables of the OCPP device model, which can be extended with new components or variables, as long as they

are optional.

Edition 2 FINAL, 2022-12-15 Generic

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 4/471 Part 2 - Specification

2. Conventions, Terminology and Abbreviations

2.1. Conventions

2.1.1. Normative

All sections and appendices are normative, unless they are explicitly indicated to be informative.

2.1.2. Requirements take precedence over text

Whenever there is any (apparent) conflict between narrative text and requirements in the specification document, the requirements

have precedence.

2.1.3. Requirement Keywords

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and

"OPTIONAL" in this document are to be interpreted as described in RFC-2119 [RFC2119], subject to the following additional

clarification clause:

The phrase "valid reasons in particular circumstances" relating to the usage of the terms "SHOULD", "SHOULD NOT",

"RECOMMENDED", and "NOT RECOMMENDED" is to be taken to mean technically valid reasons, such as the absence of necessary

hardware to support a function from a Charging Station design: for the purposes of this specification it specifically excludes

decisions made on commercial, or other non-technical grounds, such as cost of implementation, or likelihood of use.

2.1.4. Primitive Datatypes

The specification mentions the following primitive datatypes:

Table 1. Primitive Datatypes

Datatype Description

string The characters defined in the UTF-8 character set are allowed to be used.

integer

32 bit (31 bit resolution, 1 sign bit)

No leading 0’s

No plus sign

Allowed value examples: 1234, -1234

Not Allowed: 01234, +1234

decimal For data being reported by the Charging Station, the full resolution of the source data must be

preserved. The decimal sent towards the Charging Station SHALL NOT have more than six

decimal places.

identifierString This is a case-insensitive dataType and can only contain characters from the following

character set: a-z, A-Z, 0-9, '*', '-', '_', '=', ':', '+', '|', '@', '.'

dateTime All time values exchanged between CSMS and Charging Station SHALL be formatted as

defined in [RFC3339]. Additionally fractional seconds have been given an extra limit. The

number of decimal places SHALL NOT exceed the maximum of 3.

Example 1: 2019-04-12T23:20:50.52Z represents 20 minutes and 50.52 seconds after the 23rd

hour of April 12th, 2019 in UTC.

Example 2: 2019-12-19T16:39:57+01:00 represents 39 minutes and 57 seconds after the 16th

hour of December 19th, 2019 with an offset of +01:00 from UTC (Central European Time).

passwordString This is a UTF-8 encoded case-sensitive string that can only contain characters from the

following character set: "a-z", "A-Z", "0-9"

or any of the following limited set of symbols: * - _ = : + | @ .

AnyType Text, data without specified length or format.

boolean Only allowed values: "false" and "true".

Edition 2 FINAL, 2022-12-15 Generic

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 5/471 Part 2 - Specification

2.1.5. Normal communication

Unless otherwise specified, all use cases and requirements assume normal communication between Charging Station and CSMS

(Online).

2.1.6. Field description

In many cases, further explanation about how or when to use certain fields in messages and datatypes is given in the field

description. See Chapter Messages.

2.2. Terminology

2.2.1. General Terminology

This section contains the terminology that is used throughout this document.

Table 2. Terminology

Terminology Description

Application layer OSI-Layer 5-7.

Authentication Authentication is the process of confirming an identity or attribute. When speaking about

authentication one should distinguish between user authentication (e.g. sender/receiver) and

message authentication.

Block cipher Cryptographic primitive to encrypt/decrypt messages of fixed block length. Example: AES

encrypts blocks of 128 bits (16 bytes) at a time.

Cable Plugged in

In this document this can mean the following:

- Cable fixed on Charging Station side, cable plugged in to EV

- Cable plugged into the Charging Station and EV

- Wireless Charger detects an EV

Certificate A digital certificate authenticates a public key or entity. See also Public-Key Infrastructure.

Certificate Management Protocol An internet protocol used to manage X.509 digital certificates within a PKI. It is described in

RFC 4210 and uses the certificate request message format (CRMF) described in RFC 4211.

Charging Cable Cable assembly equipped with a, by the EV accepted, plug, intended to be used for the

connection between an EV and an EVSE. One side may be permanently attached to the EVSE,

or also be equipped with a plug that is accepted by the EVSE.

Charging Loop In this specification the ISO 15118-2 definition of the charging loop is used: the V2G messaging

phase for controlling the charging process by ISO 15118.

Charging Profile Generic Charging Profile, used for different types of Profiles. Contains information about the

Profile and holds the ChargingSchedule.

Charging Schedule Part of a Charging Profile. Defines a block of charging Power or Current limits. Can contain a

start time and length.

Charging Station The Charging Station is the physical system where EVs can be charged. A Charging Station

has one or more EVSEs.

Composite Charging Schedule The charging schedule as calculated by the Charging Station. It is the result of the calculation

of all active schedules and possible local limits present in the Charging Station. Local Limits

might be taken into account.

Confidentiality Only authorized entities may access confidential data. To protect data from unauthorized

access it can be encrypted. Then only entities with access to the secret keys can access the

data after decrypting it.

Connector The term Connector, as used in this specification, refers to an independently operated and

managed electrical outlet on a Charging Station. In other words, this corresponds to a single

physical Connector. In some cases an EVSE may have multiple physical socket types and/or

tethered cable/Connector arrangements(i.e. Connectors) to facilitate different vehicle types

(e.g. four-wheeled EVs and electric scooters).

Contactor An electrically controlled switching device, typically used by Charging Stations to switch

charging power on/off.

Contract Certificate A valid certificate for a charging contract in an EV for 15118 communication.

Control Pilot signal A signal used by a Charging Station to inform an EV of a maximum current limit, as defined by

IEC61851-1.

Edition 2 FINAL, 2022-12-15 Generic

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 6/471 Part 2 - Specification

Terminology Description

Cost Cost to be paid by an EV Driver for consumed energy/time etc. Including taxes.

Cryptographic hash function Cryptographic hash functions should behave as one-way functions. They must be preimage

resistant, 2nd preimage resistant, and collision-resistant. Changes in the input must produce

explicitly different results in the output. Example: SHA-256. See also ENISA OCPP Security [1].

Cryptography The ENISA Algorithms, Key Sizes and Parameters Report [1] provides an overview of the

current state of the art.

CSMS Charging Station Management System. The system that manages Charging Stations and has

the information for authorizing Users for using its Charging Stations.

Data Integrity See Integrity and Message authentication.

Digital Signature Authenticates the sender. In practice digital signatures are implemented using elliptic curves

(EC).

Encryption Using a cryptographic scheme, the message is mapped to a random-looking undecipherable

string (ciphertext). Decryption reverses the encryption process and can only be performed with

the corresponding decryption key. This decryption key is either the same as the encryption key

(symmetric cryptography) or the private key in a public-key cryptosystem. The confidentiality

of the message can be guaranteed only while the keys are kept secret.

Energy Management System A device that manages the local loads (consumption an production) based on local and/or

contractual constraints and/or contractual incentives. It has additional inputs, such as sensors

and controls from e.g. PV, battery storage.

Energy Offer Period Time during which a Charging Station is ready and willing to offer energy to an EV.

Energy Transfer Period Time during which an EV chooses to take offered energy, or return it.

EVSE An EVSE is considered as an independently operated and managed part of the Charging

Station that can deliver energy to one EV at a time.

Hash function Function that maps a message to a bit string of fixed length (hash value). See also

cryptographic hash function.

Hash value Output of a (cryptographic) hash function. The length is fixed in the specs of the hash function.

High level communication bi-directional digital communication using protocol and messages and physical and data link

layers specified in ISO 15118 series [ISO15118-1]

Idle State In both use cases and sequence diagrams, Idle status is referred as the state in which a

Charging Station is not performing any use case related tasks. Condition during which the

equipment can promptly provide a primary function but is not doing so.

Integrity Data cannot be altered without authorization. See also Message authentication.

Local Controller A logical entity between a CSMS and one or more Charging Stations that has the ability to

control charging of a group of Charging Stations based on the input from the CSMS, and can

send messages to its Charging Stations, independently of the CSMS.

Master Pass IdToken that can be used to stop any (or all) ongoing transactions. This can be used by for

example law enforcement personal to stop a transaction.

Master Pass UI Master Pass User Interface, this might be a full color touchscreen, but might also be just a

couple of buttons and LEDs and/or sounds that enable a user to select transactions to be

stopped.

Message authentication Messages should be protected against unauthorized modifications. The message should

always be sent together with an authentication tag providing its authenticity. Such an

authentication tag can be the second output of an authenticated cipher such as AES-CCM or

AES-GCM or a message authentication code.

Mode of Operation A mode of operation specifies how the message blocks are processed by the block cipher.

Using a block cipher in CBC or CTR mode provides encryption only, whereas using a block

cipher in CCM or GCM mode encrypts the plaintext and produces a message authentication

tag for the ciphertext.

OCPP-J OCPP via JSON over WebSocket.

Offline There is no communication possible between the Charging Station and CSMS. For an OCPP-J

connection this means the WebSocket connection is not open.

Password authentication The user proves his/her identity using a password or PIN.

Phase Rotation Defines the wiring order of the phases between the electrical meter (or if absent, the grid

connection), and the Charging Station Connector.

Price Specific price tag of a single tariff entry, for example: 0.35 per kWh incl. 18% VAT.

Edition 2 FINAL, 2022-12-15 Generic

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 7/471 Part 2 - Specification

Terminology Description

Public-key cryptography "Cryptographic scheme where a public key is published and henceforth can be used for

encryption of messages or verification of digital signatures. Each public key has a counterpart,

the corresponding private key. This key must be kept secret and is used for decryption or

digital signing of messages. Public-key primitives have a high computational complexity for

encryption and therefore are mostly used as part of a hybrid encryption scheme where the

public key is used to communicate a common symmetric session key under which all further

communication is encrypted. Certificates administered by a public-key infrastructure are used

to establish the authenticity of the public key. See also ENISA OCPP Security [12]. The most

popular public-key encryption scheme is RSA. Digital signatures can be generated most

efficiently with elliptic-curve based (EC) mechanisms."

Public-key infrastructure System to generate, administer, and revoke certificates.

Resume regular transaction Used in sequence diagrams to indicate that this use case/sequence diagram has ended, but

the transaction has not ended and will continue, but that is outside of scope of that specific

use case.

Requirement Provision that conveys criteria to be fulfilled. ISO/IEC Guide 2:2004, 7.5.

Security Event Any event relevant to the secure operation of the device.

Security Function Any function on the device that is needed for it to be operated securely, including access

control, authentication, and encryption.

Session A Session in OCPP is a general term that refers to the charging process of an EV, that might

include a Transaction.

Session key Symmetric key with a limited lifetime.

Symmetric cryptography Sender and receiver hold the same key. Examples for symmetric primitives are block ciphers or

MACs.

Transaction A transaction in OCPP is a part of the complete process of charging an EV that starts and

stops based on configurable parameters. These configurable parameters refer to moments in

the charging process, such as the EV being connected or the EV driver being authorized.

Tariff Collection of prices depending on charging time, power usage and other price affecting

parameters.

Use case A use case is a structured way of describing the (inter)actions necessary to achieve a certain

objective. In this document, a use case consists of an actor list, a scenario description,

postconditions and a sequence diagram and is always followed by a list of numbered

requirements.

User Authentication Verification of the identity of the communication partners (e.g., user on the device). Moreover,

verification that the communication partners are still alive throughout a session.

2.2.2. ISO 15118 and OCPP terminology mapping

This section is informative.

The ISO 15118 terminology is more comprehensive when referring to specific components within EVs and Charging Stations. The

following table shows a "mapping" of these terms.

Table 3. ISO 15118 and OCPP terminology mapping

ISO 15118 OCPP

ChargingProfile (contains the power over time the EV is planned

to consume)

Loosely corresponds to ChargingSchedule in

NotifyEVChargingSchedule message.

SASchedule (the power limits from a secondary actor for

charging an EV for a specific time)

Loosely corresponds to ChargingProfile in SetChargingProfile

message.

EVCC (i.e. Electric Vehicle Communication Controller) Controller in the EV that is used for ISO 15118 communication.

Outlet Connector

SECC (i.e. Supply Equipment Communication Controller) Controller in the EVSE of the Charging Station that is used for

ISO 15118 communication.

SA (i.e. Secondary Actor) CSMS (or other backend systems)

2.3. Abbreviations

Edition 2 FINAL, 2022-12-15 Generic

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 8/471 Part 2 - Specification

2.3.1. General Abbreviations

This section contains the abbreviations that are used throughout this document.

Table 4. Abbreviations

Abbreviation Description

AES Advanced Encryption Standard. Original name for this block cipher was Rijndael named after its designers Vincent

Rijmen and Joan Daemen.

BEV Battery Electric Vehicle

CMP Certificate Management Protocol

CS Charging Station

CSL Comma Separated List

CSMS Charging Station Management System

CSO Charging Station Operator

DHCP Dynamic Host Configuration Protocol

DNS Domain Name System

DSO Distribution System Operator

DST Daylight Saving Time

EC Elliptic Curve. See also ENISA OCPP Security [1]

ECDSA Elliptic Curve Digital Signature Algorithm.

EMS Energy Management System

ENISA European Union Agency for Network and Information Security.

EV Electric Vehicle

EVSE EV Supply Equipment IEC61851-1

FQDN Fully Qualified Domain Name

FTP(S) File Transport Protocol (Secure)

HTTP(S) HyperText Transport Protocol (Secure)

ICCID Integrated Circuit Card Identifier

IMSI International Mobile Subscription Identity

JSON JavaScript Simple Object Notation

MAC Message authentication code. Provides data integrity. Examples: CMAC, GMAC. See also ENISA OCPP Security [1].

NAT Network Address Translation

NIST National Institute of Standards and Technology.

NTP Network Time Protocol

PDU Protocol Data Unit

PHEV Plugin Hybrid Electric Vehicle

RDN Relative Distinguished Name

RSA Public-key cryptosystem named after its inventors Rivest, Shamir, and Adleman.

RSA-PSS RSA-PSS is a new signature scheme that is based on the RSA cryptosystem and provides increased security

assurance. It was added in version 2.1 of PKCS #1, following OCPP Security [23]

RST 3 phase power connection, Standard Reference Phasing

RTS 3 phase power connection, Reversed Reference Phasing

SRT 3 phase power connection, Reversed 240 degree rotation

STR 3 phase power connection, Standard 120 degree rotation

TRS 3 phase power connection, Standard 240 degree rotation

TSR 3 phase power connection, Reversed 120 degree rotation

SC Smart Charging

TLS Transport Layer Security

TSO Transmission System Operator

URI Uniform Resource Identifier RFC-3986 [RFC3986]

URL Uniform Resource Locator - refers to the subset of URIs that, in addition to identifying a resource, provide a means

of locating the resource by describing its primary access mechanism (e.g., its network "location").

Edition 2 FINAL, 2022-12-15 Generic

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 9/471 Part 2 - Specification

Abbreviation Description

UTC Coordinated Universal Time

WAN Wide Area Network.

2.3.2. ISO 15118 Abbreviations

This section contains the abbreviations from ISO 15118 that are used in this document.

Table 5. ISO 15118 Abbreviations

EIM External Identification Means

EMAID E-Mobility Account Identifier

EVCC EV Communication Controller

HLC High Level Communication

HMI Human Machine Interface

LAN Local Area Network

MO Mobility Operator

OEM Original Equipment Manufacturer

OCSP Online Certificate Status Protocol

PWM Pulse Width Modulation

SA Secondary Actor

SECC Supply Equipment Communication Controller

V2G Vehicle to Grid

2.4. Actors

This section is informative.

In OCPP, system actors are covering functions or devices.

Table 6. Actors

Actor name Actor type Actor description

EV Driver Actor The Driver of an EV who wants to charge the EV at a Charging Station.

Connector Device The term "Connector", as used in this specification, refers to an independently

operated and managed electrical outlet on a Charging Station. In other words,

this corresponds to a single physical Connector. In some cases an EVSE may

have multiple Connectors: multiple physical socket types and/or types (e.g.

four-wheeled EVs and electric scooters).

CSMS System Charging Station Management System: manages Charging Stations and has

the information for authorizing Users for using its Charging Stations.

Charging Station Device The Charging Station is the physical system where an EV can be charged. A

Charging Station has one or more EVSEs.

Charging Station

Operator

Actor A party that manages a CSMS.

Electric Vehicle Device Electric Vehicle, distributed energy resource with a remote battery and socket.

Local Controller Device A logical entity between a CSMS and one or more Charging Stations that has

the ability to control charging of a group of Charging Stations based on the

input from the CSMS.

External Control System Actor An external system that may impose charging limits/constraints on the

Charging Station or CSMS, for example a DSO or EMS.

Edition 2 FINAL, 2022-12-15 Generic

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 10/471 Part 2 - Specification

2.5. References

2.5.1. Generic references

Table 7. References

Reference Description

[DNP3] Distributed Network Protocol. https://www.dnp.org/About/Overview-of-DNP3-Protocol

[EMI3-BO] "eMI3 standard version V1.0" http://emi3group.com/documents-links/

[IEC60870-5-104] Set of standards which define systems used for telecontrol (supervisory control and data

acquisition) in electrical engineering and power system automation applications.

https://webstore.iec.ch/publication/3755

[IEC61850-7-420] Communications standard for distributed energy resources (DER). https://webstore.iec.ch/

publication/6019

[IEC61851-1] "IEC 61851-1 2017: EV conductive charging system - Part 1: General requirements"

https://webstore.iec.ch/publication/33644

[IEC62196] IEC 62196: Plugs, socket-outlets, vehicle couplers and vehicle inlets - Conductive charging of

electric vehicles. https://webstore.iec.ch/publication/6582

[ISO15118-1] ISO 15118-1 specifies terms and definitions, general requirements and use cases as the basis for

the other parts of ISO 15118. It provides a general overview and a common understanding of

aspects influencing the charge process, payment and load leveling. https://webstore.iec.ch/

publication/9272

[ISO15118-2] Road vehicles – Vehicle to grid communication interface – Part 2: Technical protocol description

and Open Systems Interconnection (OSI) layer requirements, Document Identifier: 69/216/CDV.

https://webstore.iec.ch/publication/9273

[ISO4217] "ISO 4217: Currency codes" http://www.iso.org/iso/home/standards/currency_codes.htm

[OCPP2.0-PART4] "OCPP 2.0.1: Part 4 - JSON over WebSockets implementation guide".

http://www.openchargealliance.org/downloads/

[OpenADR] "Open Automated Demand Response" http://www.openadr.org/

[RFC1321] "The MD5 Message-Digest Algorithm" https://tools.ietf.org/html/rfc1321

[RFC2119] "Key words for use in RFCs to Indicate Requirement Levels". S. Bradner. March 1997.

http://www.ietf.org/rfc/rfc2119.txt

[RFC3339] "Date and Time on the Internet: Timestamps" https://tools.ietf.org/html/rfc3339

[RFC3986] "Uniform Resource Identifier (URI): Generic Syntax" https://tools.ietf.org/html/rfc3986

[RFC5646] "Tags for Identifying Languages" https://tools.ietf.org/html/rfc5646

2.5.2. Security related references

Table 8. Security related references

Reference Description

[1] ENISA European Network and Information Security Agency, Algorithms, key size and parameters report 2014, 2014.

(last accessed on 17 January 2016) https://www.enisa.europa.eu/publications/algorithms-key-size-and-parameters-

report-2014

[2] National Institute of Standards and Technology. FIPS PUB 140-2, Security Requirements for Cryptographic Modules,

May 2001. http://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.140-2.pdf

[3] Cooper, D., et al., Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile,

Internet Engineering Task Force, Request for Comments 5280, May 2008, http://www.ietf.org/rfc/rfc5280.txt

[4] Dierks, T. and Rescorla, E., The Transport Layer Security (TLS) Protocol Version 1.2, Internet Engineering Task Force,

Request for Comments 5246, August 2008, http://www.ietf.org/rfc/rfc5246.txt

[5] Eastlake, D., Transport Layer Security (TLS) Extensions: Extension Definitions, Internet Engineering Task Force,

Request for Comments 6066, January 2011, http://www.ietf.org/rfc/rfc6066.txt

[6] McGrew, D. and Bailey, D., AES-CCM Cipher Suites for Transport Layer Security (TLS), Internet Engineering Task Force,

Request for Comments 6655, July 2012, http://www.ietf.org/rfc/rfc6655.txt

[7] Rescorla E. et al., Transport Layer Security (TLS) Renegotiation Indication Extension, Internet Engineering Task Force,

Request for Comments 5746, February 2010, http://www.ietf.org/rfc/rfc5746.txt

Edition 2 FINAL, 2022-12-15 Generic

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 11/471 Part 2 - Specification

Reference Description

[8] "Russel Housley, Tim Polk, Warwick Ford, and David Solo. Internet Public Key Infrastructure: X.509 Certificate and

Certificate Revocation List (CRL) Profile, RFC 3280, April 2002." https://www.ietf.org/rfc/rfc3280.txt

[9] Pettersen. "The Transport Layer Security (TLS) Multiple Certificate Status Request Extension." RFC 6961, June 2013.

https://tools.ietf.org/html/rfc6961.

[10] Hollenbeck, S., "Transport Layer Security Protocol Compression Methods", RFC 3749, May 2004.

https://www.ietf.org/rfc/rfc3749.txt

[11] National Institute of Standards and Technology. Annex C: Approved Random Number Generators for FIPS PUB 140-2

[25], February 2012. https://csrc.nist.gov/csrc/media/publications/fips/140/2/final/documents/fips1402annexc.pdf

[12] Bundesamt für Sicherheit in der Informationstechnik: Anwendungshinweise und Interpretationen zum Schema, AIS

20, Funktionalitätsklassen und Evaluationsmethodologie für deterministische Zufallszahlengeneratoren, Version 3.0,

Bonn, Germany, May 2013. (in German) https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/Zertifizierung/

Interpretationen/AIS_20_pdf.html

[13] Bundesamt für Sicherheit in der Informationstechnik: Anwendungshinweise und Interpretationen zum Schema, AIS

31, Funktionalitätsklassen und Evaluationsmethodologie für physikalische Zufallszahlengeneratoren, Version 3.0,

Bonn, Germany, May 2013. (in German) https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/Zertifizierung/

Interpretationen/AIS_31_pdf.html

[14] "OWASP - Transport Layer Protection Cheat Sheet. https://www.owasp.org/index.php/

Transport_Layer_Protection_Cheat_Sheet#Extended_Validation_Certificates "

[15] P. Hoffman and W.C.A. Wijngaards, Elliptic Curve Digital Signature Algorithm (DSA) for DNNSEC, Internet Engineering

Task Force (IETF) RFC 6605, April 2012. http://www.ietf.org/rfc/rfc6605.txt

[16] Adams, C., Farrell, S., Kause, T., and T. Mononen, "Internet X.509 Public Key Infrastructure Certificate Management

Protocol (CMP)", RFC 4210, September 2005. https://www.ietf.org/rfc/rfc4210.txt

[17] National Institute of Standards and Technology. Special Publication 800-57 Part 1 Rev. 4, Recommendation for Key

Management. January 2016. https://csrc.nist.gov/publications/detail/sp/800-57-part-1/rev-4/final

[18]

RFC 2617. HTTP Authentication: Basic and Digest Access Authentication. https://www.ietf.org/rfc/rfc2617.txt

[19] RFC 5280. Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile.

https://www.ietf.org/rfc/rfc5280.txt

[20] OCPP 1.6. Interface description between Charging Station and CSMS. October 2015.

http://www.openchargealliance.org/downloads/

[21] Eekelen, M. van, Poll, E., Hubbers, E., Vieira, B., Broek, F. van den: An end-to-end security design for smart EV-charging

for Enexis and ElaadNL by LaQuSo1. December 2, 2014. https://www.elaad.nl/smart-charging-end2end-security-

design/

[22]

RFC 2986. PKCS #10: Certification Request Syntax Specification, Version 1.7. https://www.ietf.org/rfc/rfc2986.txt

[23]

RSA-PSS. https://tools.ietf.org/html/rfc8017

[24] Santesson, et al. "X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP" RFC 6960. June

2013. https://tools.ietf.org/html/rfc6960

[25]

RFC 2818. HTTP Over TLS. https://tools.ietf.org/html/rfc2818

2.6. Definition of Transaction

This section is informative.

To support as many business cases as possible, and to prevent too many messages being sent when not needed for certain

business cases, OCPP 2.0.1 supports flexible configuration of the start and stop of a transaction. This makes it possible to define

the start and stop of a transaction depending on market demands.

See: Flexible transaction start/stop for more information.

2.6.1. Transaction in relation to Energy Transfer Period

The Energy Transfer Period is a period of time during which energy is transferred between the EV and the EVSE. There MAY be

multiple Energy Transfer Periods during a Transaction.

Multiple Energy Transfer Periods can be separated by either:

Edition 2 FINAL, 2022-12-15 Generic

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 12/471 Part 2 - Specification

• an EVSE-initiated suspense of transfer during which the EVSE does not offer energy transfer, or;

• an EV-initiated suspense of transfer during which the EV remains electrically connected to the EVSE, or;

• an EV-initiated suspense of transfer during which the EV is not electrically connected to the EVSE.

Transaction

Energy Offer

Energy Flow

Transaction

Transaction start is configured

via configuration Variable:

TxStartPoint

EnergyOfferPeriod

Energy Offer Period starts when

the EVSE is ready and willing to

supply energy.

EnergyTransferPeriod

Energy is transferred.

During an EnergyOfferPeriod there may

be periods the EV is not charging due to

for instance, warm/full battery or EV

internal smart charging.

EnergyTransferPeriod

Energy is transferred.

EnergyOfferSuspendPeriod

During a transaction, there may be periods

the EnergyOffer to EV is suspended by the

EVSE, for instance due to Smart Charging

or local balancing.

EnergyOfferPeriod

EnergyTransferPeriod

Energy is transferred.

Transaction stop is configured

via configuration Variable:

TxStopPoint

Figure 1. OCPP Charging Transaction definition

Edition 2 FINAL, 2022-12-15 Generic

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 13/471 Part 2 - Specification

2.7. ISO 15118 support

This section is informative.

This version of OCPP supports ISO 15118 authorization (also called "Plug and Charge") and ISO 15118 based Smart Charging. (See

[ISO15118-2]) Furthermore it describes how to install and update ISO 15118 certificates. These 3 functionalities are not included as

one functional block, but are included in multiple chapters throughout the specification. ISO 15118 authorization is included in the

functional block Authorization and the Smart Charging use cases for ISO 15118 are included in the chapter Smart Charging.

Certificate handling is described in a separate functional block.

Implementors of 15118 need to be aware of timeout constraints enforced by 15118, see [ISO15118-1] (Page: 127, Table: 109)

For reference, the current timing constrains for 15118 edition 1 are:

Table 9. ISO 15118 Timing constrains

Timeout Default

Sequence Timeouts 60 seconds

Sequence Performance Timeouts 40 seconds

PaymentDetailsReq/Res 5 seconds

CertificateUpdateReq/Res 5 seconds

CertificateInstallationReq/Res 5 seconds

Edition 2 FINAL, 2022-12-15 Generic

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 14/471 Part 2 - Specification

3. Generic Requirements

This section is normative.

The generic requirements build the basis for defining the use case elements described in the Functional Blocks.

Table 10. Generic requirements

ID Precondition Requirement definition Note

FR.01 The sender of a <message>Request

SHALL wait for a

<message>Response or a timeout,

before sending another request

message.

FR.02 When the Charging Station receives a

valid OCPP request message

according to the JSON schemas / RPC

Framework AND

the other system is not causing a

security violation

The Charging Station SHALL respond

with a RPC Framework: CALLRESULT.

If the Charging Station/CSMS needs to

provide additional information, this

can be done in the statusInfo element

of the response message.

FR.03 When the Charging Station/CSMS

receives an invalid OCPP message

according to the JSON schemas / RPC

Framework OR

the other system causes a security

violation

The Charging Station/CSMS SHALL

respond with a RPC Framework:

CALLERROR.

FR.04 When the CSMS did not accept the

BootNotificationRequest from the

Charging Station AND

The Charging Station sends a

message other than

BootNotificationRequest

The CSMS SHALL respond with a RPC

Framework: CALLERROR:

SecurityError.

FR.05 There are a few messages that do not

provide their result in the response

message, but send one or more

messages that contain the result.

When one of the following messages

is received; GetReport, GetBaseReport,

GetMonitoringReport,

GetDisplayMessages,

CustomerInformation,

GetChargingProfiles, GetLog,

UpdateFirmware, PublishFirmware,

TriggerMessage(<message>)

The Charging Station SHALL

acknowledge the requests in the list

below with a response message first,

before sending the follow-up message

shown after the arrow (→):

GetReport → NotifyReport

GetBaseReport → NotifyReport

GetMonitoringReport →

NotifyMonitoringReport

GetDisplayMessages →

NotifyDisplayMessage

CustomerInformation →

NotifyCustomerInformation

GetChargingProfiles →

ReportChargingProfiles

GetLog → LogStatusNotification

UpdateFirmware →

FirmwareStatusNotification

PublishFirmware →

PublishFirmwareStatusNotification

TriggerMessage(<message>) →

The CSMS needs to know that a

request was accepted, so that it can

expect result messages.

3.1. Time Format Requirements

This section is normative.

All time values exchanged between CSMS and Charging Station SHALL be formatted as defined in RFC-3339 [RFC3339].

Additionally fractional seconds have been given an extra limit. The number of decimal places SHALL NOT exceed the maximum of

Edition 2 FINAL, 2022-12-15 Generic

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 15/471 Part 2 - Specification

3. However, it is RECOMMENDED to omit fractional seconds entirely, because it is of limited use and omitting it reduces data

usages.

It is strongly RECOMMENDED to exchange all time values between CSMS and Charging Station as UTC, with the time zone

designator 'Z', as specified by RFC-3339 [RFC3339]. This will improve interoperability between CSMS and Charging Station.

3.1.1. Displaying local time

When a Charging Station wants to give detailed control of configuring the internal clock to a CSO, it can implement one or more of

the following Configuration Variables: TimeSource, TimeZone, TimeOffset, NtpSource, NtpServerUri.

3.1.1.1. Daylight Saving Time

There are 2 ways a Charging Station can support punctual automated bi-annual changeover between "standard time" and "daylight

saving time" periods.

• The transition dates and offsets are known in the Charging Station, based on the configured TimeZone.

• The transition date and offset is manually configured for every transition via: NextTimeOffsetTransitionDateTime

and TimeOffsetNextTransition.

Daylight saving time is used for displaying the current time to the EV driver.

3.2. Message Timeouts

This section is normative.

OCPP does not specify timing requirements for messages. Timing of messages is greatly influenced by the underlying network

used. A GPRS network has different timing characteristics compared to a land-line. As OCPP does not require a certain type of

network, but leaves this open for the CSO to select, OCPP cannot require timing constrains.

If you are looking for some guidance, start with a 30 second timeout on message requests, and tune it for the network used.

The message timeout setting in a Charging Station can be configured in the messageTimeout field in the

NetworkConnectionProfile. The purpose of the message timeout is to be able to consider a request message as not sent and

continue with other tasks when the message did not arrive due to communication errors or software failure. For transaction related

events, use case E13 - Transaction-related message not accepted by CSMS describes the retry procedure when this happens. See

also the section Delivering transaction-related messages in Functional Block E.

A charging station may discover that the connection to CSMS is not functioning correctly when it gets a timeout to a request or

when the websocket ping is not answered. In such a situation it is advised that the charging station drops the connection and then

reconnects to CSMS. This will create a fresh session and will possibly connect to a different endpoint of a multi-instance CSMS,

which may resolve the error.

3.3. Language support

This section is informative.

A CSMS can provide the Charging Station with preferred languages for an EV Driver, enabling the Charging Station to communicate

with the EV Driver in a language according to his/her preferences.

For any Charging Station that shows messages on a display it is RECOMMENDED to at least also implement these in "English".

When the preferred languages for an EV-driver (provided by the CSMS) are not "English" and don’t match any of the other languages

implemented in the Charging Station, it is RECOMMENDED to use "English" as fall-back.

Edition 2 FINAL, 2022-12-15 Generic

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 16/471 Part 2 - Specification

A. Security

Edition 2 FINAL, 2022-12-15 A. Security

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 17/471 Part 2 - Specification

1. OCPP Security

This Functional Block describes the security requirements for the OCPP protocol. The security part was developed to strengthen

and mature the future development and standardization of OCPP. It is based amongst others on the end-to-end security design by

LaQuSo [21]. Security requirements are included on security measures at Charging Station and CSMS, to support users of the

OCPP.

1.1. Security Objectives

This section is informative.

OCPP security has been designed to meet the following security objectives:

1. To allow the creation of a secure communication channel between the CSMS and Charging Station. The integrity and

confidentiality of messages on this channel should be protected with strong cryptographic measures.

2. To provide mutual authentication between the Charging Station and the CSMS. Both parties should be able to identify who

they are communicating with.

3. To provide a secure firmware update process by allowing the Charging Station to check the source and the integrity of

firmware images, and by allowing non-repudiation of these images.

4. To allow logging of security events to facilitate monitoring the security of the smart charging system. A list of security

related events and their 'criticality' is provided in the appendices.

1.2. Design Considerations

This section is informative.

The security Functional Block was designed to fit into the approach taken in OCPP. Standard web technologies are used whenever

possible to allow cost-effective implementations using available web libraries and software. No application layer security measures

are included. Based on these considerations, OCPP security is based on TLS and public key cryptography using X.509 certificates.

Because the CSMS usually acts as the server, different users or role-based access control on the Charging Station are not

implemented in this standard. To mitigate this, it is recommended to implement access control on the CSMS. To make sure the

mechanisms implemented there cannot be bypassed, OCPP should not be used by qualified personnel performing maintenance to

Charging Stations locally at the Charging Station, as other protocols may be used for local maintenance purposes.

Edition 2 FINAL, 2022-12-15 A. Security

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 18/471 Part 2 - Specification

1.3. Security Profiles

This section defines the different OCPP security profiles and their requirement. OCPP 2.0.1 supports three security profiles:

The table below shows which security measures are used by which profile.

Table 11. Overview of OCPP security profiles

Profile Charging Station

Authentication

CSMS

Authentication

Communication

Security

1. Unsecured Transport with Basic

Authentication

HTTP Basic Authentication - -

2. TLS with Basic Authentication HTTP Basic Authentication

TLS authentication

using certificate

Transport Layer Security

(TLS)

3. TLS with Client Side Certificates

TLS authentication

using certificate

TLS authentication

using certificate

Transport Layer Security

(TLS)

• The Unsecured Transport with Basic Authentication Profile does not include authentication for the CSMS, or measures to

set up a secure communication channel. Therefore, it should only be used in trusted networks, for instance in networks

where there is a VPN between the CSMS and the Charging Station. For field operation it is highly recommended to use a

security profile with TLS.

• In some cases (e.g. lab installations, test setups, etc.) one might prefer to use OCPP 2.0.1 without implementing security.

While this is possible, it is NOT considered a valid OCPP 2.0.1 implementation.

• When the Charging Station does not have the correct date and time set, it cannot validate the server certificate. A solution

for this might be to either use NTP, mobile network to set time automatically, or have an installer tool that sets the time

before the first connection.

1.3.1. Generic Security Profile requirements

Table 12. Generic Security Profile requirements

ID Precondition Requirement definition

A00.FR.001 The Charging Station and CSMS SHALL only use one security profile at a

time

A00.FR.002 If the Charging Station tries to

connect with a different profile than

the CSMS is using

The CSMS SHALL terminate the connection.

A00.FR.003 If the CSMS tries to connect with a

different profile than the Charging

Station is using

The Charging Station SHALL terminate the connection.

A00.FR.004 The security profile SHALL be configured before OCPP communication is

possible.

A00.FR.005 Lowering the security profile that is used, to a less secure profile, is for

security reasons, not part of the OCPP specification, and MUST be done

through another method, not via OCPP. OCPP messages SHALL NOT be

used for this (e.g. SetVariablesRequest or DataTransferRequest).

A00.FR.006 When a CSMS communicates with

Charging Stations with different

security profiles or different versions

of OCPP.

The CSMS MAY operate the Charging Stations via different addresses or

ports of the CSMS.

For instance, the CSMS server may have one TCP port for TLS with Basic

Authentication, and another port for TLS with Client Side Certificates.

In this case there is only one security profile in use per port of the CSMS,

which is allowed.

1.3.2. Unsecured Transport with Basic Authentication Profile - 1

Table 13. Security Profile 1 - Unsecured Transport with Basic Authentication

No. Type Description

1 Name Unsecured Transport with Basic Authentication

2 Profile No. 1

Edition 2 FINAL, 2022-12-15 A. Security

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 19/471 Part 2 - Specification

No. Type Description

3 Description The Unsecured Transport with Basic Authentication profile provides a low level of security.

Charging Station authentication is done through a username and password. No measures are

included to secure the communication channel.

4 Charging Station

Authentication

For Charging Station authentication HTTP Basic authentication is used.

5 CSMS Authentication In this profile, the CSMS does not authenticate itself to the Charging Station. The Charging Station

has to trust that the server it connects to is indeed the CSMS.

6 Communication

Security

No communication security measures are included in the profile.

Charging Station

CSMS

HTTP GET / ProtectedData (clear text communication)

HTTP/401 Authorization Required

HTTP GET / ProtectedData

Authorization Basic

Username / Password

HTTP 200 / ProtectedData

Application Data

Figure 2. Sequence Diagram: HTTP Basic Authentication sequence diagram

7 Remark(s) Please note, that the encoding of the basic authentication password in OCPP 2.0.1 (A00.FR.205)

differs from how this was done in OCPP 1.6.

1.3.3. Unsecured Transport with Basic Authentication Profile - Requirements

Table 14. Security Profile 1 - Unsecured Transport with Basic Authentication - Requirements

ID Precondition Requirement definition

A00.FR.201 The Unsecured Transport with Basic Authentication Profile SHOULD only

be used in trusted networks.

A00.FR.202 The Charging Station SHALL authenticate itself to the CSMS using HTTP

Basic authentication [18]

A00.FR.203 A00.FR.202 The client, i.e. the Charging Station, SHALL provide a username and

password with every connection request.

A00.FR.204 A00.FR.203 The username SHALL be equal to the Charging Station identity, which is

the identifying string of the Charging Station as it uses it in the OCPP-J

connection URL. When using Basic Authentication, the Charging Station

identity may not contain the character ":". Otherwise the CSMS may be

unable to separate the username from the password.

A00.FR.205 The password SHALL be stored in the BasicAuthPassword

Configuration Variable. It SHALL be a randomly chosen passwordString

with a sufficiently high entropy, consisting of minimum 16 and maximum

40 characters (alpha-numeric characters and the special characters

allowed by passwordString). The password SHALL be sent as a UTF-8

encoded string (NOT encoded into octet string or base64).

A00.FR.206 A00.FR.203 With HTTP Basic, the username and password are transmitted in clear

text, encoded in base64 only. Hence, it is RECOMMENDED that this

mechanism will only be used over connections that are already secured

with other means, such as VPNs.

A00.FR.207 A00.FR.202 The CSMS SHALL validate that Charging Station identity and the Basic

Authentication password match with username and password in the

authorization header of the connection request.

Edition 2 FINAL, 2022-12-15 A. Security

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 20/471 Part 2 - Specification

1.3.4. TLS with Basic Authentication Profile - 2

Table 15. Security Profile 2 - TLS with Basic Authentication

No. Type Description

1 Name TLS with Basic Authentication

2 Profile No. 2

3 Description In the TLS with Basic Authentication profile, the communication channel is secured using

Transport Layer Security (TLS). The CSMS authenticates itself using a TLS server certificate. The

Charging Stations authenticate themselves using HTTP Basic Authentication.

4 Charging Station

Authentication

For Charging Station authentication HTTP Basic authentication is used.

Because TLS is used in this profile, the password will be sent encrypted, reducing the risks of

using this authentication method.

5 CSMS Authentication The Charging Station authenticates the CSMS via the TLS server certificate.

6 Communication

Security

The communication between Charging Station and CSMS is secured using TLS.

Charging Station

CSMS

Client Hello

Server Hello

Server Certificate

Server Hello Done

ClientKeyExchange

[ChangeCipherSpec]

Finished

[ChangeCipherSpec]

Finished

HTTP GET / ProtectedData (Encrypted Communication)

HTTP/401 Authentication Required

HTTP GET / ProtectedData

Authorization Basic

Username/Password

HTTP 200 / ProtectedData

Application Data

Figure 3. Sequence Diagram: TLS with Basic Authentication sequence diagram

Edition 2 FINAL, 2022-12-15 A. Security

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 21/471 Part 2 - Specification

7 Remark(s) TLS allows a number of configurations, not all of which provide sufficient security. The

requirements below describe the configurations allowed for OCPP.

The Charging Station should include the same header as used in Basic Auth RFC 2617, while

requesting to upgrade the http connection to a websocket connection as described in RFC 6455.

The server first needs to validate the Authorization header before upgrading the connection.

Example:

GET /ws HTTP/1.1

Remote-Addr: 127.0.0.1

UPGRADE: websocket

CONNECTION: Upgrade

HOST: 127.0.0.1:9999

ORIGIN: http://127.0.0.1:9999

SEC-WEBSOCKET-KEY: Pb4obWo2214EfaPQuazMjA==

SEC-WEBSOCKET-VERSION: 13

AUTHORIZATION: Basic <Base64 encoded(<ChargePointId>:<AuthorizationKey>)>

Please note, that the encoding of the basic authentication password in OCPP 2.0.1 (A00.FR.304)

differs from how this was done in OCPP 1.6.

1.3.5. TLS with Basic Authentication Profile - Requirements

Table 16. Security Profile 2 - TLS with Basic Authentication - Requirements

ID Precondition Requirement definition

A00.FR.301 The Charging Station SHALL authenticate itself to the CSMS using HTTP

Basic authentication [18]

A00.FR.302 A00.FR.301 The client, i.e. the Charging Station, SHALL provide a username and

password with every connection request.

A00.FR.303 A00.FR.302 The username SHALL be equal to the Charging Station identity, which is

the identifying string of the Charging Station as it uses it in the OCPP-J

connection URL. When using Basic Authentication, the Charging Station

identity may not contain the character ":". Otherwise the CSMS may be

unable to separate the username from the password.

A00.FR.304 A00.FR.302 The password SHALL be stored in the BasicAuthPassword

Configuration Variable. It SHALL be a randomly chosen passwordString

with a sufficiently high entropy, consisting of minimum 16 and maximum

40 characters (alpha-numeric characters and the special characters

allowed by passwordString). The password SHALL be sent as a UTF-8

encoded string (NOT encoded into octet string or base64).

A00.FR.306 The CSMS SHALL act as the TLS server.

A00.FR.307 The CSMS SHALL authenticate itself by using the CSMS certificate as

server side certificate.

A00.FR.308 The Charging Station SHALL verify the certification path of the CSMS’s

certificate according to the path validation rules established in Section 6

of [3].

A00.FR.309 The Charging Station SHALL verify that the commonName includes the

CSMS’s FQDN.

A00.FR.310 If the CSMS does not own a valid

certificate, or if the certification path

is invalid

The Charging Station SHALL trigger an InvalidCsmsCertificate security

event (See part 2 appendices for the full list of security events).

A00.FR.311 A00.FR.310 The Charging Station SHALL terminate the connection.

A00.FR.312 The communication channel SHALL be secured using Transport Layer

Security (TLS) [4].

A00.FR.313 The Charging Station and CSMS SHALL only use TLS v1.2 or above.

A00.FR.314 Both of these endpoints SHALL check the version of TLS used.

Edition 2 FINAL, 2022-12-15 A. Security

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 22/471 Part 2 - Specification

ID Precondition Requirement definition

A00.FR.315

A00.FR.314

AND

The CSMS detects that the Charging

Station only allows connections

using an older version of TLS, or

only allows SSL

The CSMS SHALL terminate the connection.

A00.FR.316

A00.FR.314

AND

The Charging Station detects that

the CSMS only allows connections

using an older version of TLS, or

only allows SSL

The Charging Station SHALL trigger an InvalidTLSVersion security event

AND terminate the connection (See part 2 appendices for the full list of

security events).

A00.FR.317 TLS SHALL be implemented as in [4] or its successor standards without

any modifications.

A00.FR.318

The CSMS SHALL support at least the following four cipher suites:

TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256

TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384

TLS_RSA_WITH_AES_128_GCM_SHA256

TLS_RSA_WITH_AES_256_GCM_SHA384

Note: The CSMS will have to provide 2 different certificates to support

both cipher suites. Also when using security profile 3, the CSMS should be

capable of generating client side certificates for both cipher suites.

A00.FR.319

The Charging Station SHALL support at least the cipher suites:

(TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256

AND

TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384)

(TLS_RSA_WITH_AES_128_GCM_SHA256

AND

TLS_RSA_WITH_AES_256_GCM_SHA384)

Note 1: TLS_RSA does not support forward secrecy, therefore TLS_ECDHE

is RECOMMENDED. Furthermore, if the Charging Station detects an

algorithm used that is not secure, it SHOULD trigger an

InvalidTLSCipherSuite security event (See part 2 appendices for the full

list of security events).

Note 2: Please note that ISO15118-2 prescribes to implement the

following cipher suites for the communication between EV and Charging

Station:

TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256,

TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256

A00.FR.320 The Charging Station and CSMS SHALL NOT use cipher suites that use

cryptographic primitives marked as unsuitable for legacy use in [1]. This

will mean that when one (or more) of the cipher suites described in this

specification becomes marked as unsuitable for legacy use, it SHALL NOT

be used anymore.

A00.FR.321 The TLS Server and Client SHALL NOT use TLS compression methods to

avoid compression side-channel attacks and to ensure interoperability as

described in Section 6 of [10].

A00.FR.322

A00.FR.320

AND

The CSMS detects that the Charging

Station only allows connections

using one of these suites

The CSMS SHALL terminate the connection.

Edition 2 FINAL, 2022-12-15 A. Security

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 23/471 Part 2 - Specification

ID Precondition Requirement definition

A00.FR.323

A00.FR.320

AND

The Charging Station detects that

the CSMS only allows connections

using one of these suites

The Charging Station SHALL trigger an InvalidTLSCipherSuite security

event AND terminate the connection (See part 2 appendices for the full list

of security events).

A00.FR.324 A00.FR.302 The CSMS SHALL validate that Charging Station identity and the Basic

Authentication password match with username and password in the

authorization header of the connection request.

1.3.6. TLS with Client Side Certificates Profile - 3

Table 17. Security Profile 3 - TLS with Client Side Certificates

No. Type Description

1 Name TLS with Client Side Certificates

2 Profile No. 3

3 Description In the TLS with Client Side Certificates profile, the communication channel is secured using

Transport Layer Security (TLS). Both the Charging Station and CSMS authenticate themselves

using certificates.

4 Charging Station

Authentication

The CSMS authenticates the Charging Station via the TLS client certificate.

5 CSMS Authentication The Charging Station authenticates the CSMS via the TLS server certificate.

6 Communication

Security

The communication between Charging Station and CSMS is secured using TLS.

Charging Station

CSMS

Client Hello

Server Hello

Server Certificate

Certificate Server Request

Server Hello Done

Client Certificate

Client Key Exchange

Certificate Verify

[ChangeCipherSpec]

Finished

[ChangeCipherSpec]

Finished

Application Data (Authenticated and encrypted communication)

Figure 4. Sequence Diagram: TLS with Client Side Certificates

7 Remark(s) N/a

1.3.7. TLS with Client Side Certificates Profile - Requirements

Table 18. Security Profile 3 - TLS with Client Side Certificates - Requirements

ID Precondition Requirement definition

A00.FR.401 The Charging Station SHALL authenticate itself to the CSMS using the

Charging Station certificate.

A00.FR.402 The Charging Station certificate SHALL be used as a TLS client side

certificate

A00.FR.403 The CSMS SHALL verify the certification path of the Charging Station’s

certificate according to the path validation rules established in Section 6

of [3]

Edition 2 FINAL, 2022-12-15 A. Security

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 24/471 Part 2 - Specification

ID Precondition Requirement definition

A00.FR.404 The CSMS SHALL verify that the certificate is owned by the CSO (or an

organization trusted by the CSO) by checking that the O

(organizationName) RDN in the subject field of the certificate contains

the CSO name.

A00.FR.405 The CSMS SHALL verify that the certificate belongs to this Charging

Station by checking that the CN (commonName) RDN in the subject field of

the certificate contains the unique serial number of the Charging Station

(see Certificate Properties).

A00.FR.406 If the Charging Station certificate is

not owned by the CSO, for instance

immediately after installation

it is RECOMMENDED to update the certificate before continuing

communication with the Charging Station (also see Installation)

A00.FR.407

NOT A00.FR.429 AND

If the Charging Station does not own

a valid certificate, or if the

certification path is invalid

The CSMS SHALL terminate the connection.

A00.FR.408 A00.FR.407 OR A00.FR.429 It is RECOMMENDED to log a security event

InvalidChargingStationCertificate in the CSMS.

A00.FR.409 The CSMS SHALL act as the TLS server.

A00.FR.410 The CSMS SHALL authenticate itself by using the CSMS certificate as

server side certificate.

A00.FR.411 The Charging Station SHALL verify the certification path of the CSMS’s

certificate according to the path validation rules established in Section 6

of [3].

A00.FR.412 The Charging Station SHALL verify that the commonName matches the

CSMS’s FQDN.

A00.FR.413 If the CSMS does not own a valid

certificate, or if the certification path

is invalid

The Charging Station SHALL trigger an InvalidCsmsCertificate security

event (See part 2 appendices for the full list of security events).

A00.FR.414 A00.FR.413 The Charging Station SHALL terminate the connection.

A00.FR.415 The communication channel SHALL be secured using Transport Layer

Security (TLS) [4].

A00.FR.416 The Charging Station and CSMS SHALL only use TLS v1.2 or above.

A00.FR.417 Both of these endpoints SHALL check the version of TLS used.

A00.FR.418

A00.FR.417

AND

The CSMS detects that the Charging

Station only allows connections

using an older version of TLS, or

only allows SSL

The CSMS SHALL terminate the connection.

A00.FR.419

A00.FR.417

AND

The Charging Station detects that

the CSMS only allows connections

using an older version of TLS, or

only allows SSL

The Charging Station SHALL trigger an InvalidTLSVersion security event

AND terminate the connection (See part 2 appendices for the full list of

security events).

A00.FR.420 TLS SHALL be implemented as in [4] or its successor standards without

any modifications.

A00.FR.421

The CSMS SHALL support at least the following four cipher suites:

TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256

TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384

TLS_RSA_WITH_AES_128_GCM_SHA256

TLS_RSA_WITH_AES_256_GCM_SHA384

Note: The CSMS will have to provide 2 different certificates to support

both cipher suites. Also when using security profile 3, the CSMS should be

capable of generating client side certificates for both cipher suites.

Edition 2 FINAL, 2022-12-15 A. Security

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 25/471 Part 2 - Specification

ID Precondition Requirement definition

A00.FR.422

The Charging Station SHALL support at least the cipher suites:

(TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256

AND

TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384)

(TLS_RSA_WITH_AES_128_GCM_SHA256

AND

TLS_RSA_WITH_AES_256_GCM_SHA384)

Note 1: TLS_RSA does not support forward secrecy, therefore TLS_ECDHE

is RECOMMENDED. Furthermore, if the Charging Station detects an

algorithm used that is not secure, it SHOULD trigger an

InvalidTLSCipherSuite security event (See part 2 appendices for the full

list of security events).

Note 2: Please note that ISO15118-2 prescribes to implement the

following cipher suites for the communication between EV and Charging

Station:

TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256,

TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256

A00.FR.423 The Charging Station and CSMS SHALL NOT use cipher suites that use

cryptographic primitives marked as unsuitable for legacy use in [1]. This

will mean that when one (or more) of the cipher suites described in this

specification becomes marked as unsuitable for legacy use, it SHALL NOT

be used anymore.

A00.FR.424 The TLS Server and Client SHALL NOT use TLS compression methods to

avoid compression side-channel attacks and to ensure interoperability as

described in Section 6 of [10].

A00.FR.425

A00.FR.424

AND

If the CSMS detects that the

Charging Station only allows

connections using one of these

suites

The CSMS SHALL terminate the connection.

A00.FR.426

A00.FR.424

AND

The Charging Station detects that

the CSMS only allows connections

using one of these suites

The Charging Station SHALL trigger an InvalidTLSCipherSuite security

event AND terminate the connection (See part 2 appendices for the full list

of security events).

A00.FR.427 A unique Charging Station certificate SHALL be used for each Charging

Station.

A00.FR.428 The Charging Station Certificate MAY be the same certificate as the SECC

Certificate in ISO15118-2, used to set up a TLS connection between the

Charging Station and an Electric Vehicle.

A00.FR.429 If Charging Station certificate has

been expired AND

CSMS has been explicitly configured

to accept a connection by this

specific Charging Station with an

expired certificate.

CSMS MAY accept this Charging Station in a BootNotification - Pending

state (use case B02) after which it SHALL immediately execute A02 -

Update Charging Station Certificate by request of CSMS to renew the

certificate.

1.4. Keys used in OCPP

This section is normative.

OCPP uses a number of public private key pairs for its security, see below Table. To manage the keys on the Charging Station,

messages have been added to OCPP. Updating keys on the CSMS or at the manufacturer is out of scope for OCPP. If TLS with

Client Side certificates is used, the Charging Station requires a "Charging Station certificate" for authentication against the CSMS.

Edition 2 FINAL, 2022-12-15 A. Security

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 26/471 Part 2 - Specification

Table 19. Certificates used in the OCPP security specification

Certificate Private Key Stored At Description

CSMS Certificate CSMS Key used to authenticate the CSMS.

Charging Station Certificate Charging Station Key used to authenticate the Charging Station.

Firmware Signing Certificate Manufacturer Key used to verify the firmware signature.

SECC Certificate Charging Station Certificate used by ISO15118-2 to set up a TLS

connection between the Charging Station and

an Electric Vehicle.

1.4.1. Certificate Properties

This section is normative.

Table 20. Certificate Properties requirements

ID Precondition Requirement definition

A00.FR.501 All certificates SHALL use a private key that provides security equivalent

to a symmetric key of at least 112 bits according to Section 5.6.1 of [17].

This is the key size that NIST recommends for the period 2011-2030.

A00.FR.502

A00.FR.501

AND

RSA or DSA

This translates into a key that SHALL be at least 2048 bits long.

A00.FR.503

A00.FR.501

AND

elliptic curve cryptography

This translates into a key that SHALL be at least 224 bits long.

A00.FR.504 For all cryptographic operations, only the algorithms recommended by BSI

in [12], which are suitable for use in future systems, SHALL be used. This

restriction includes the signing of certificates in the certificate hierarchy

A00.FR.505 For signing by the certificate authority RSA-PSS, or ECDSA SHOULD be

used.

A00.FR.506 For computing hash values the SHA256 algorithm SHOULD be used.

A00.FR.507 The certificates SHALL be stored and transmitted in the X.509 format

encoded in Privacy-Enhanced Mail (PEM) format.

A00.FR.508 All certificates SHALL include a serial number.

A00.FR.509 The subject field of the certificate SHALL contain the organization name

of the certificate owner in the O (organizationName) RDN.

A00.FR.510 For the CSMS certificate, the subject field SHALL contain the FQDN of the

endpoint of the server in the CN (commonName) RDN.

A00.FR.511 For the Charging Station certificate, the subject field SHALL contain a CN

(commonName) RDN which consists of the unique serial number of the

Charging Station. This serial number SHALL NOT be in the format of a

URL or an IP address so that Charging Station certificates can be

differentiated from CSMS certificates.

Note: According to RFC 2818, if a subjectAltName extension of type

dnsName is present, that must be used as the identity. This would be

incompliant with OCPP and ISO 15118. Therefore it SHOULD NOT be used

in Charging Station and CSMS certificates.

It is allowed to use the subjectAltName extension of type dnsName for a

CSMS, when the CSMS has multiple network paths to reach it (for

example, via a private APN + VPN using its IP address in the VPN and via

public Internet using a named URL).

A00.FR.512 For all certificates the X.509 Key Usage extension [19] SHOULD be used to

restrict the usage of the certificate to the operations for which it will be

used.

A00.FR.513 If the Charging Station Certificate is also used as SECC Certificate in the

ISO 15118 protocol, the certificate SHOULD also meet the requirements in

ISO15118-2.

Edition 2 FINAL, 2022-12-15 A. Security

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 27/471 Part 2 - Specification

ID Precondition Requirement definition

A00.FR.514 For all certificates it is strongly RECOMMENDED NOT to use the X.509

Extended Key Usage extension, to be compatible with the ISO 15118

standard. There are alternative mechanisms available.

1.4.2. Certificate Hierarchy

This section is normative.

The OCPP protocol supports the use of two separate certificate hierarchies:

1. The Charging Station Operator hierarchy which contains the CSMS, and Charging Station certificates.

2. The Manufacturer hierarchy which contains the Firmware Signing certificate.

The CSMS can update the CSO root certificates stored on the Charging Station using the InstallCertificateRequest message.

Table 21. Certificate Hierarchy requirements

ID Precondition Requirement definition

A00.FR.601 The Charging Station Operator MAY act as a certificate authority for the

Charging Station Operator hierarchy

A00.FR.602 A00.FR.601 The Charging Station Operator MAY for instance follow the certificate

hierarchy described in Appendices E and F of ISO15118-2 and use the

CSO Sub-CA 2 certificate to sign the CSMS and Charging Station

certificates. This could give the advantage that the online verification of

Charging Station client side certificates can be done within the Charging

Station Operator’s networks, simplifying the network architecture.

A00.FR.603 The private keys belonging to the CSO root certificates MUST be well

protected.

A00.FR.604 As the Manufacturer is usually a separate organization from the Charging

Station Operator, a trusted third party SHOULD be used as a certificate

authority. This is essential to have non-repudiation of firmware images.

1.5. Certificate Revocation

This section is normative.

In some cases a certificate may become invalid prior to the expiration of the validity period. Such cases include changes of the

organization name, or the compromise or suspected compromise of the certificate’s private key. In such cases, the certificate

needs to be revoked or indicate it is no longer valid. The revocation of the certificate does not mean that the connection needs to

be closed as the the connection can stay open longer than 24 hours.

Different methods are recommended for certificate revocation, see below Table.

Table 22. Recommended revocation methods for the different certificates.

Certificate Revocation

CSMS certificate Fast expiration

Charging Station certificate Online verification

Firmware Signing certificate Online verification

Table 23. Certificate Revocation requirements

ID Precondition Requirement definition

A00.FR.701 Fast expiration SHOULD be used to revoke the CSMS certificate. (See

Note 1)

A00.FR.702 The CSMS SHOULD use online certificate verification to verify the validity

of the Charging Station certificates.

A00.FR.703 It is RECOMMENDED that a separate certificate authority server is used to

manage the certificates.

A00.FR.704 A00.FR.703 This server SHOULD also keep track of which certificates have been

revoked.

Edition 2 FINAL, 2022-12-15 A. Security

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 28/471 Part 2 - Specification

ID Precondition Requirement definition

A00.FR.705 The CSMS SHALL verify the validity of the certificate with the certificate

authority server. (See Note 2)

A00.FR.707 Prior to providing the certificate for firmware validation to the Charging

Station, the CSMS SHOULD validate both, the certificate and the signed

firmware update.

Note 1: With fast expiration, the certificate is only valid for a short period, less than 24 hours. After that the server needs to request

a new certificate from the Certificate Authority, which may be the CSO itself (see section Certificate Hierarchy). This prevents the

Charging Stations from needing to implement revocation lists or online certificate verification. This simplifies the implementation

of certificate management at the Charging Station and reduces communication costs at the Charging Station side. By requiring fast

expiration, if the certificate is compromised, the impact is reduced to only a short period.

When the certificate chain should becomes compromised, attackers could used forged certificates to trick a Charging Station to

connect to a "fake" CSMS. By using fast expiration, the time a Charging Station is vulnerable is greatly reduced.

The Charging Station always communicates with the Certificate Authority through the CSMS, this way, if the Charging Station is

compromised, the Charging Station cannot attack the CA directly.

Note 2: This allows for immediate revocation of Charging Station certificates. Revocation of Charging Station certificates will

happen for instance when a Charging Station is removed. This is more common than revoking the CSMS certificate, which is

normally only done when it is compromised.

1.6. Installation

This section is normative.

Unique credentials should be used to authenticate each Charging Station to the CSMS, whether they are the password used for

HTTP Basic Authentication (see Charging Station Authentication) or the Charging Station certificate. These unique credentials have

to be put on the Charging Station at some point during manufacturing or installation.

Table 24. Certificate Installation requirements

ID Precondition Requirement definition

A00.FR.801 It is RECOMMENDED that the manufacturer initializes the Charging Station

with unique credentials during manufacturing.

A00.FR.802 A00.FR.801 The credentials SHOULD be generated using a cryptographic random

number generator, and installed in a secure environment.

A00.FR.803 A00.FR.801 They SHOULD be sent to the CSO over a secure channel, so that the CSO

can import them in the CSMS

A00.FR.804 If Charging Station certificates are

used.

The manufacturer MAY sign these using their own certificate.

A00.FR.805 A00.FR.804 It is RECOMMENDED that the CSO immediately updates the credentials

after installation using the methods described in Section A01 - Update

Charging Station Password for HTTP Basic Authentication or A02 - Update

Charging Station Certificate by request of CSMS.

A00.FR.806 Before the 'factory credentials' have

been updated

The CSMS MAY restrict the functionality that the Charging Station can

use. The CSMS can use the BootNotification state: Pending for this.

During the Pending state, the CSMS can update the credentials.

A00.FR.807

A00.FR.804 AND

Charging Station manufacturer

certificate has expired

The CSMS MAY accept a connection by Charging Station in a Pending

state after the BootNotification and immediately execute use case A02 -

Update Charging Station Certificate by request of CSMS to install a new

valid CSO certificate.

Edition 2 FINAL, 2022-12-15 A. Security

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 29/471 Part 2 - Specification

2. Use cases & Requirements

A01 - Update Charging Station Password for HTTP Basic Authentication

Table 25. A01 - Password Management

No. Type Description

1 Name Update Charging Station Password for HTTP Basic Authentication

2 ID A01

Functional block A. Security

3 Objective(s) This use case defines how to use the BasicAuthPassword, the password used to authenticate

Charging Stations in the Basic and TLS with Basic Authentication security profiles.

4 Description To enable the CSMS to configure a new password for HTTP Basic Authentication, the CSMS can

send a new value for the BasicAuthPassword Configuration Variable.

Actors Charging Station, CSMS

Scenario description 1. The CSMS sends a SetVariablesRequest(ComponentName=SecurityCtrlr,

VariableName=BasicAuthPassword) to the Charging Station.

2. The Charging Station responds with SetVariablesResponse and the status Accepted.

3. The Charging Station disconnects its current connection. (Storing any queued messages)

4. The Charging Station connects to the CSMS with the new password.

5 Prerequisite(s) Security Profile: Basic Security Profile or TLS with Basic Authentication in use.

6 Postcondition(s)

Successful postcondition:

The Charging Station has reconnected to the CSMS with the new password.

Failure postcondition:

If the Charging Station responds to the SetVariablesRequest with a SetVariablesResponse with a

status other than Accepted, the Charging Station will keep using the old credentials. The CSMS

might treat the Charging Station differently, e.g. by not accepting the Charging Station’s boot

notifications.

CSMS

Charging Station

SetVariablesRequest(BasicAuthPassword)

SetVariablesResponse(status = Accepted)

disconnect

connect (using new password)

Figure 5. Update Charging Station Password for HTTP Basic Authentication (happy flow)

7 Error handling n/a

8 Remark(s) n/a

A01 - Update Charging Station Password for HTTP Basic Authentication -

Requirements

Table 26. A01 - Update Charging Station Password for HTTP Basic Authentication - Requirements

ID Precondition Requirement definition

A01.FR.01 The password SHALL be stored in the configuration variable

BasicAuthPassword.

Edition 2 FINAL, 2022-12-15 A. Security

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 30/471 Part 2 - Specification

ID Precondition Requirement definition

A01.FR.02 To set a Charging Station’s basic authorization password via OCPP, the

CSMS SHALL send the Charging Station a SetVariablesRequest

message with the BasicAuthPassword Configuration Variable.

A01.FR.03

A01.FR.02

AND

The Charging Station responds to this

SetVariablesRequest with a

SetVariablesResponse with status

Accepted.

The CSMS SHALL assume that the authorization key change was

successful, and no longer accept the credentials previously used by the

Charging Station.

A01.FR.04

A01.FR.02

AND

The Charging Station responds to this

SetVariablesRequest with a

SetVariablesResponse with status other

than Accepted

The CSMS SHALL assume that the Charging Station has NOT changed

the password. Therefore the CSMS SHALL keep accepting the old

credentials.

A01.FR.05 A01.FR.04 While the CSMS SHALL still accepts a connection from the Charging

Station, it MAY restrict the functionality that the Charging Station can

use. The CSMS can use the BootNotification state: Pending for this.

During the Pending state, the CSMS can for example retry to update the

credentials.

A01.FR.06 Different passwords SHOULD be used for different Charging Stations.

A01.FR.07 Passwords SHOULD be generated randomly to ensure that the

passwords have sufficient entropy.

A01.FR.08 the CSMS SHOULD only store salted password hashes, not the

passwords themselves.

A01.FR.09 the CSMS SHOULD NOT put the passwords in clear-text in log files or

debug information. In this way, if the CSMS is compromised not all

Charging Station password will be immediately compromised.

A01.FR.10 On the Charging Station the password needs to be stored in clear-text.

Extra care SHOULD be taken into storing it securely. Definitions of

mechanisms how to securely store the credentials are however not in

scope of the OCPP Security Profiles.

A01.FR.11 A01.FR.02 The Charging Station SHALL log the change of an

BasicAuthPassword in the Security log.

A01.FR.12 A01.FR.11 The Charging Station SHALL NOT disclose the content of the

BasicAuthPassword in its logging. This is to prevent exposure of key

material to persons that may have access to a diagnostics file.

A02 - Update Charging Station Certificate by request of CSMS

Table 27. A02 - Update Charging Station Certificate by request of CSMS

No. Type Description

1 Name Update Charging Station Certificate by request of CSMS

2 ID A02

Functional block A. Security

3 Objective(s) To facilitate the management of the Charging Station client side certificate, a certificate update

procedure is provided.

4 Description The CSMS requests the Charging Station to update its key using TriggerMessageRequest with the

requestedMessage field set to SignChargingStationCertificate (or SignV2GCertificate for separate

15118 certificate).

Actors Charging Station, CSMS, Certificate Authority Server

Edition 2 FINAL, 2022-12-15 A. Security

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 31/471 Part 2 - Specification

No. Type Description

Scenario description 1. The CSMS requests the Charging Station to update its certificate using the

TriggerMessageRequest with the requestedMessage field set to SignChargingStationCertificate

(or SignV2GCertificate for separate 15118 certificate).

2. The Charging Station responds with TriggerMessageResponse

3. The Charging Station generates a new public / private key pair.

4. The Charging Station sends a SignCertificateRequest to the CSMS containing the applicable

CertificateSigningUse .

5. The CSMS responds with SignCertificateResponse, with status Accepted.

6. The CSMS forwards the CSR to the Certificate Authority Server.

7. Certificate Authority Server signs the certificate.

8. The Certificate Authority Server returns the Signed Certificate to the CSMS.

9. The CSMS sends CertificateSignedRequest to the Charging Station.

10. The Charging Station verifies the Signed Certificate.

11. The Charging Station responds with CertificateSignedResponse to the CSMS with the status

Accepted or Rejected.

5 Prerequisite(s) The standard configuration variable OrganizationName MUST be set.

6 Postcondition(s)

Successful postcondition:

New Client Side certificate installed in the Charging Station.

Failure postcondition:

New Client Side certificate is rejected and discarded.

CSMS

Charging Station

Certificate Authority Server

CS certificate is almost due

TriggerMessageRequest(SignCertificate)

TriggerMessageResponse(Accepted)

generate new

public / private key pair

SignCertificateRequest(csr)

SignCertificateResponse(Accepted)

forward CSR

sign certificate

return Signed Certificate

CertificateSignedRequest(certificate)

Verify validity

of signed certificate

CertificateSignedResponse (Accepted/Rejected)

opt

[key valid]

Switch to new certificate

Figure 6. Update Charging Station Certificate

Edition 2 FINAL, 2022-12-15 A. Security

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 32/471 Part 2 - Specification

7 Error handling The CSMS accepts the CSR request from the Charging Station, before forwarding it to the CA. But

when the CA cannot be reached, or rejects the CSR, the Charging Station will never known. The

CSMS may do some checks on the CSR, but cannot do all the checks that a CA does, and it does

not prevent connection timeout to the CA. When something like this goes wrong, either the CA is

offline or the CSR send by the Charging Station is not correct, according to the CA. In both cases

this is something an operator at the CSO needs to be notified of. The operator then needs to

investigate the issue. When resolved, the operator can re-run A02.

It is NOT RECOMMENDED to let the Charging Station retry when the certificate is not send within

X minutes or hours. When the CSR is incorrect, that will not be resolved automatically. It is

possible that only a new firmware will fix this.

8 Remark(s) The Charging Station Operator may act as a certificate authority for the Charging Station Operator

hierarchy.

The applicable Certification Authority SHALL check the information in the CSR.

If it is correct, the Certificate Authority SHALL sign the CSR, send it to the CSO, the CSO sends it

back to the Charging Station in the CertificateSignedRequest message.

The certificate authority SHOULD implement strong measures to keep the certificate signing

private keys secure.

Even though the messages CertificateSignedRequest (see use cases A02 and A03) and

InstallCertificateRequest (use case M05 - Install CA Certificate in a Charging Station) are both

used to send certificates, their purposes are different. CertificateSignedRequest is used to return

the the Charging Stations own public certificate and V2G certificate(s) signed by a Certificate

Authority. InstallCertificateRequest is used to install Root certificates.

For V2G certificate handling see use cases M03 - Retrieve list of available certificates from a

Charging Station, M04 - Delete a specific certificate from a Charging Station and M06 - Get

Charging Station Certificate status.

A02 - Update Charging Station Certificate by request of CSMS - Requirements

Table 28. A02 - Requirements

ID Precondition Requirement definition

A02.FR.01 A key update SHOULD be performed after installation of the Charging

Station, to change the key from the one initially provisioned by the

manufacturer (possibly a default key).

A02.FR.02 After sending a

TriggerMessageResponse.

The Charging Station SHALL generate a new public / private key pair using

one of the key generation functions described in Section 4.2.1.3 of [16].

A02.FR.03 A02.FR.02 The Charging Station SHALL send the public key in form of a Certificate

Signing Request (CSR) as described in RFC 2986 [22] and then PEM

encoded, using the SignCertificateRequest message.

A02.FR.04 The CSMS SHOULD NOT sign the certificate itself, but instead forwards

the CSR to a dedicated certificate authority server managing the

certificates for the Charging Station infrastructure. The dedicated

authority server MAY be operated by the CSO.

A02.FR.05 The private key generated by the Charging Station during the key update

process SHALL NOT leave the Charging Station at any time, and SHALL

NOT be readable via OCPP or any other (remote) communication

connection.

A02.FR.06 The Charging Station SHALL verify the validity of the signed certificate in

the CertificateSignedRequest message, checking at least the period when

the certificate is valid, the properties in Certificate Properties, and that it is

part of the Charging Station Operator certificate hierarchy as described in

Certificate Hierarchy.

A02.FR.07 If the certificate is not valid. The Charging Station SHALL respond to the CertificateSignedRequest

with status Rejected AND discard the certificate AND trigger an

InvalidChargingStationCertificate security event (See part 2 appendices for

the full list of security events).

Edition 2 FINAL, 2022-12-15 A. Security

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 33/471 Part 2 - Specification

ID Precondition Requirement definition

A02.FR.08 The Charging Station SHALL switch to the new certificate as soon as the

current date and time is after the 'Not valid before' field in the certificate

(e.g. by closing the websocket and TLS connection and reconnecting with

the new certificate).

A02.FR.09 If the Charging Station contains

more than one valid certificate of

the ChargingStationCertificate type.

The Charging Station SHALL use the newest certificate, as measured by

the start of the validity period.

A02.FR.10

A02.FR.09

AND When the Charging Station has

validated that the new certificate

works

The Charging Station MAY discard the old certificate. It is

RECOMMENDED to store old certificates for one month, as fallback.

A02.FR.11 Upon receipt of a

SignCertificateRequest AND

It is able to process the request

The CSMS SHALL set status to Accepted in the SignCertificateResponse.

A02.FR.12 Upon receipt of a

SignCertificateRequest AND

It is NOT able to process the request

The CSMS SHALL set status to Rejected in the SignCertificateResponse.

A02.FR.13 When using different certificates for

15118 connections and the

Charging Station to CSMS

connection

The Charging Station SHALL set the certificateType field in the

SignCertificateRequest to the certificate for which the update was

triggered.

A02.FR.14 When receiving a

SignCertificateRequest with

certificateType included

It is RECOMMENDED for the CSMS to set the certificateType field in the

CertificateSignedRequest to the type of certificate in the

SignCertificateRequest.

A02.FR.15 If the Charging Station contains

more than one valid V2G certificate,

derived from the same root

certificate.

The Charging Station SHALL use the newest certificate, as measured by

the start of the validity period.

A02.FR.16 If the configuration variable

MaxCertificateChainSize is

implemented AND

The Charging Station receives a

CertificateSignedRequest message

with a certificate (chain) with with a

size that exceeds the set value

configured at

MaxCertificateChainSize

The Charging Station SHALL respond with a CertificateSignedResponse

message with status Rejected .

A02.FR.17 When the CSMS accepted the

SignCertificateRequest for a CSR

AND

the Charging Station did not yet

receive a CertificateSignedRequest

for this CSR AND

the number of seconds configured

at CertSigningWaitMinimum has

expired

The Charging Station SHALL send a new SignCertificateRequest for the

CSR. Optionally, this CSR MAY be for a newly generated key pair.

A02.FR.18 A02.FR.17 The Charging Station SHALL double the previous back-off time, starting

with the number of seconds configured at CertSigningWaitMinimum, every

time the back-off time expires without having received the

CertificateSignedRequest for this CSR.

A02.FR.19

A02.FR.18 AND

The maximum number of

increments is reached

The Charging Station SHALL stop resending the SignCertificateRequest,

until it is requested by the CSMS via a TriggerMessageRequest for

SignChargingStationCertificate, SignV2GCertificate or

SignCombinedCertificate.

A02.FR.20 A02.FR.07 The Charging Station SHALL NOT initiate the back-off mechanism and

resend the SignCertificateRequest, until this is requested by the CSMS via

a TriggerMessageRequest for SignChargingStationCertificate,

SignV2GCertificate or SignCombinedCertificate.

Edition 2 FINAL, 2022-12-15 A. Security

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 34/471 Part 2 - Specification

ID Precondition Requirement definition

A02.FR.21 When the Charging Station receives

a SignCertificateResponse with

status Rejected, in response to a

SignCertificateRequest with

certificateType V2GCertificate

It is RECOMMENDED to turn off ISO15118PnCEnabled until the Charging

Station has been rebooted.

A03 - Update Charging Station Certificate initiated by the Charging

Station

Table 29. A03 - Update Charging Station Certificate initiated by the Charging Station

No. Type Description

1 Name Update Charging Station Certificate initiated by the Charging Station

2 ID A03

Functional block A. Security

3 Objective(s) To facilitate the management of the Charging Station client side certificate, a certificate update

procedure is provided.

4 Description The Charging Station detects that the certificate (ChargingStationCertificate or V2GCertificate for

15118) it is using will expire in one month. The Charging Station initiates the process to update its

key using SignCertificateRequest, indicating the requested certificate in the CertificateSigningUse

field.

Actors Charging Station, CSMS, Certificate Authority Server

Scenario description

1. The Charging Station detects that the Charging Station certificate is due to expire.

2. The Charging Station generates a new public / private key pair.

3. The Charging Station sends a SignCertificateRequest to the CSMS containing the applicable

CertificateSigningUse.

4. The CSMS responds with a SignCertificateResponse, with status Accepted.

5. The CSMS forwards the CSR to the Certificate Authority Server.

6. Certificate Authority Server signs the certificate.

7. The Certificate Authority Server returns the Signed Certificate to the CSMS.

8. The CSMS sends a CertificateSignedRequest to the Charging Station.

9. The Charging Station verifies the Signed Certificate.

10. The Charging Station responds with a CertificateSignedResponse to the CSMS with the status

Accepted or Rejected.

5 Prerequisite(s) The standard configuration variable OrganizationName MUST be set.

6 Postcondition(s)

Successful postcondition:

New Client Side certificate installed in the Charging Station.

Failure postcondition:

New Client Side certificate is rejected and discarded.

Edition 2 FINAL, 2022-12-15 A. Security

OCPP 2.0.1 Edition 2 - © Open Charge Alliance 2022 35/471 Part 2 - Specification

Charging Station

CSMS

Certificate Authority Server

CS certificate is almost due

generate new public / private key pair

SignCertificateRequest(csr)

SignCertificateResponse(Accepted)

forward CSR

sign certificate

return Signed Certificate

CertificateSignedRequest(certificate)

Verify validity of signed certificate

CertificateSignedResponse (Accepted/Rejected)

opt

[key valid]

Switch to new certificate

Figure 7. Update Charging Station Certificate initiated by Charging Station